Producing alternative segmentations of data into blocks in a data deduplication system

ABSTRACT

For producing secondary segmentations of data into blocks and corresponding digests for input data in a data deduplication system using a processor device in a computing environment, digests are calculated for an input data chunk using a primary segmentation into blocks. Secondary segmentations are produced for each of the data mismatches based on reference data, and used to calculate further data matches. The primary segmentation and the corresponding primary digests are stored for the input data chunk.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is cross-related to the following seventeen applications each listed as:

U.S. application Ser. Nos. 13/941,703, 13/941,873, 13/941,694, 13/941,886, 13/941,896, 13/941,951, 13/941,711, 13/941,958, 13/941,714, 13/941,742, 13/941,769, 13/941,782, 13/941,800, 13/941,999, 13/942,009, 13/942,027, and 13/942,048, all of which are filed on the same day as the present invention and the entire contents of which are incorporated herein by reference and are relied upon for claiming the benefit of priority.

BACKGROUND OF THE INVENTION

Field of the Invention

The present invention relates in general to computers, and more particularly to producing alternative segmentations of data into blocks in a data deduplication system in a computing environment.

Description of the Related Art

In today's society, computer systems are commonplace. Computer systems may be found in the workplace, at home, or at school. Computer systems may include data storage systems, or disk storage systems, to process and store data. Large amounts of data have to be processed daily and the current trend suggests that these amounts will continue being ever-increasing in the foreseeable future. An efficient way to alleviate the problem is by using deduplication. The idea underlying a deduplication system is to exploit the fact that large parts of the available data are copied again and again, by locating repeated data and storing only its first occurrence. Subsequent copies are replaced with pointers to the stored occurrence, which significantly reduces the storage requirements if the data is indeed repetitive.

SUMMARY OF THE DESCRIBED EMBODIMENTS

In one embodiment, a method is provided for producing a multiplicity of secondary segmentations of data into blocks and corresponding digests for input data in a data deduplication system using a processor device in a computing environment. In one embodiment, by way of example only, digests are calculated for an input data chunk using a primary segmentation into blocks. Secondary segmentations are produced for each of the data mismatches based on reference data, and used to calculate further data matches. The primary segmentation and the corresponding primary digests are stored for the input data chunk.

In another embodiment, a computer system is provided for producing a multiplicity of secondary segmentations of data into blocks and corresponding digests for input data in a data deduplication system using a processor device, in a computing environment. The computer system includes a computer-readable medium and a processor in operable communication with the computer-readable medium. In one embodiment, by way of example only, the processor, calculates digests for an input data chunk using a primary segmentation into blocks. Secondary segmentations are produced for each of the data mismatches based on reference data, and used to calculate further data matches. The primary segmentation and the corresponding primary digests are stored for the input data chunk.

In a further embodiment, a computer program product is provided for producing a multiplicity of secondary segmentations of data into blocks and corresponding digests for input data in a data deduplication system using a processor device, in a computing environment. The computer-readable storage medium has computer-readable program code portions stored thereon. The computer-readable program code portions include a first executable portion that calculates digests for an input data chunk using a primary segmentation into blocks. Secondary segmentations are produced for each of the data mismatches based on reference data, and used to calculate further data matches. The primary segmentation and the corresponding primary digests are stored for the input data chunk.

In addition to the foregoing exemplary method embodiment, other exemplary system and computer product embodiments are provided and supply related advantages. The foregoing summary has been provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in the background.

BRIEF DESCRIPTION OF THE DRAWINGS

In order that the advantages of the invention will be readily understood, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict embodiments of the invention and are not therefore to be considered to be limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

FIG. 1 is a block diagram illustrating a computing system environment having an example storage device in which aspects of the present invention may be realized;

FIG. 2 is a block diagram illustrating a hardware structure of data storage system in a computer system in which aspects of the present invention may be realized;

FIG. 3 is a flowchart illustrating an exemplary method for digest retrieval based on similarity search in deduplication processing in a data deduplication system in which aspects of the present invention may be realized;

FIG. 4 is a flowchart illustrating an exemplary alternative method for digest retrieval based on similarity search in deduplication processing in a data deduplication system in which aspects of the present invention may be realized;

FIG. 5 is a flowchart illustrating an exemplary method for efficient calculation of both similarity search values and boundaries of digest blocks using a single linear calculation of rolling hash values in a data deduplication system in which aspects of the present invention may be realized;

FIG. 6 is a block diagram illustrating calculating rolling hash values in which aspects of the present invention may be realized;

FIG. 7 is a block diagram illustrating an exemplary structure for finding additional identical data with secondary segmentation in which aspects of the present invention may be realized;

FIG. 8 is a block diagram illustrating a method for finding additional identical data using a secondary segmentation in which aspects of the present invention may be realized; and

FIG. 9 is a flowchart illustrating an exemplary method for producing and using secondary segmentations derived from references in a data deduplication system in which aspects of the present invention may be realized.

DETAILED DESCRIPTION OF THE DRAWINGS

Data deduplication is a highly important and vibrant field in computing storage systems. Data deduplication refers to the reduction and/or elimination of redundant data. In data deduplication, a data object, which may be a file, a data stream, or some other form of data, is partitioned into one or more parts called chunks or blocks. In a data deduplication process, duplicate copies of data are reduced or eliminated, leaving a minimal amount of redundant copies, or a single copy of the data, respectively. The goal of a data deduplication system is to store a single copy of duplicated data, and the challenges in achieving this goal are efficiently finding the duplicate data patterns in a typically large repository, and storing the data patterns in a storage efficient deduplicated form. A significant challenge in deduplication storage systems is scaling to support very large repositories of data. Such large repositories can reach sizes of Petabytes (1 Petabyte=2⁵⁰ bytes) or more. Deduplication storage systems supporting such repository sizes, must provide efficient processing for finding duplicate data patterns within the repositories, where efficiency is measured in resource consumption for achieving deduplication (resources may be CPU cycles, RAM storage, persistent storage, networking, etc.).

For example, in one embodiment, a hash-based deduplication process includes the following operations: segmenting the input data into segments; calculating a cryptographic hash value, denoted herewith as a digest, for each segment; and looking up the hash value in an index of known hash values. If the hash value is found, the data is already stored and does not need to be stored again, hence the deduplication.

In one embodiment, a variety of techniques may be used to segment a stream of bytes based on the data itself. A segmenting process starts with a calculation of rolling hash values for the input data, producing a hash value for each window of bytes (also denoted as a seed) at each byte position in the data, as shown below in FIG. 6. If this hash value matches some criterion or criteria, then a segment boundary is declared. More complex segmentation methods also take into account neighboring boundaries, the relation between them or their segment sizes, the history of segmentation, etc. The rolling hash values are calculated based on a sliding window of bytes. There is a trade-off with regards to the size of the sliding window of bytes based on which the rolling hash values are calculated. If this sliding window is small, the rolling hash values are based on fewer bytes thus constituting a less reliable random variable, and also reducing the statistical significance of the segmenting calculations which are based on these values. If the sliding window is large, then each rolling hash value is more sensitive to changes in the data (namely, a given change in the data affects more hash values), thus making the segmenting positions more sensitive to changes in the data, as depicted below in FIG. 7, thus allowing minor or otherwise localized changes in the input data to alter the segmentation in an undesirable way. In other words, whether the window size is increased or decreased, both directions have a negative effect on the quality of the block segmentation. Considering the trade-off specified above, a need exists to use additional information to facilitate and improve the quality of block segmentation.

Thus, in one embodiment, a deduplication storage system may be based on maintaining a search optimized index of values known as fingerprints or digests, where a small fingerprint represents a larger block of data in the repository. The fingerprint values may be cryptographic hash values calculated based on the blocks' data. In one embodiment, secure hash algorithm (SHA), e.g. SHA-1 or SHA-256, which are a family of cryptographic hash functions, may be used. Identifying fingerprint matches, using index lookup, enables to store references to data that already exists in a repository. In one embodiment, determining segment boundaries can be based on the data itself.

To provide reasonable deduplication in this approach, the mean size of the data blocks based on which fingerprints are generated must be limited to smaller sizes and may not be too large. The reason being that a change of a bit within a data block will probabilistically change the data block's corresponding fingerprint, and thus having large data blocks makes the scheme more sensitive to updates in the data as compared to having small blocks. A typical data block size may range from 4 KB to 64 KB, depending on the type of application and workload. Thus, by way of example only, small data blocks may range in sizes of up to 64 KB, and large data blocks are those data blocks having a size larger than 64 KB.

To support very large repositories scaling to Petabytes (e.g., repositories scaling to at least one Petabyte), the number of fingerprints to store coupled with the size of a fingerprint (ranging between 16 bytes and 64 bytes), becomes prohibitive. For example, for 1 Petabyte of deduplicated data, with a 4 KB mean data block size, and 32 bytes fingerprint size (e.g. of SHA-256), the storage required to store the fingerprints is 8 Terabytes. Maintaining a search optimized data structure for such volumes of fingerprints is difficult, and requires optimization techniques. However existing optimization techniques do not scale to these sizes while maintaining performance. For this reason, to provide reasonable performance, the supported repositories have to be relatively small (on the order of tens of TB). Even for such smaller sizes, considerable challenges and run-time costs arise due to the large scale of the fingerprint indexes, that create a bottle-neck (e.g., chunk look disk bottleneck) in deduplication processing. A solid-state disk (SSD) to cache parts of the index in low persistent memory may be used but such is limited by the size and cost of the SSD.

To solve this problem, in one embodiment, a deduplication system may be based on a two-step approach for searching data patterns during deduplication. In the first step, a large chunk of incoming data (e.g. a few megabytes) is searched in the repository for similar (rather than identical) data chunks of existing data, and the incoming data chunk is partitioned accordingly into intervals and paired with corresponding (similar) repository intervals. In the second step, a byte-wise matching algorithm is applied on pairs of similar intervals, to identify identical sub-intervals, which are already stored in a repository of data. The matching algorithm of the second step relies on reading all the relevant similar data in the repository in order to compare it byte-wise to the input data.

Yet, a problem stemming from a byte-wise comparison of data underlying the matching algorithm of the second step, is that data of roughly the same size and rate as the incoming data should be read from the repository, for comparison purposes. For example, a system processing 1 GB of incoming data per second, should read about 1 GB of data per second from the repository for byte-wise comparison. This requires substantially high capacities of I/O per second of the storage devices storing the repository data, which in turn increases their cost.

Additional trends in information technology coinciding with the above problem are the following: (1) Improvements in the computing ability by increasing CPU speeds and the number of CPU cores. (2) Increase in disk density, while disk throughput remains relatively constant or improving only modestly. This means that there are fewer spindles relative to the data capacity, thus practically reducing the overall throughput. Due to the problem specified above, there is a need to design an alternative solution, to be integrated in a two step deduplication system embodiment specified above, that does not require reading from the repository in high rates/volumes.

Therefore, in one embodiment, by way of example only, additional embodiments address these problem, as well as shifts resource consumption from disks to the CPUs, to benefit from the above trends. The embodiments described herein are integrated within the two step and scalable deduplication embodiments embodiment described above, and uses a similarity search to focus lookup of digests during deduplication. In one embodiment, a global similarity search is used as a basis for focusing the similarity search for digests of repository data that is most likely to match input data.

The embodiments described herein significantly reduce the capacity of I/O per second required of underlying disks, benefit from the increases in computing ability and in disk density, and considerably reduce the costs of processing, as well as maintenance costs and environmental overhead (e.g. power consumption).

In one embodiment, input data is segmented into small segments (e.g. 4 KB) and a digest (a cryptographic hash value, e.g. SHA1) is calculated for each such segment. First, a similarity search algorithm, as described above, is applied on an input chunk of data (e.g. 16 MB), and the positions of the most similar reference data in the repository are located and found. These positions are then used to lookup the digests of the similar reference data. The digests of all the data contained in the repository are stored and retrieved in a form that corresponds to their occurrence in the data. Given a position of a section of data contained in the repository, the digests associated with the section of data are efficiently located in the repository and retrieved. Next, these reference digests are loaded into memory, and instead of comparing data to find matches, the input digests and the loaded reference digests are matched.

The described embodiments provide a new fundamental approach for architecting a data deduplication system, which integrates a scalable two step approach of similarity search followed by a search of identical matching segments, with an efficient and cost effective digest/fingerprint based matching algorithm (instead of byte-wise data comparison). The digest/fingerprint based matching algorithm enables to read only a small fraction (1%) of the volume of data required by byte-wise data comparison. The present invention proposed herein, a deduplication system can provide high scalability to very large data repositories, in addition to high efficiency and performance, and reduced costs of processing and hardware.

In one embodiment, by way of example only, the term “similar data” may be referred to as: for any given input data, data which is similar to the input data is defined as data which is mostly the same (i.e. not entirely but at least 50% similar) as the input data. From looking at the data in a binary view (perspective), this means that similar data is data where most (i.e. not entirely but at least 50% similar) of the bytes are the same as the input data.

In one embodiment, by way of example only, the term “similar search” may be referred to as the process of searching for data which is similar to input data in a repository of data. In one embodiment, this process may be performed using a search structure of similarity elements, which is maintained and searched within.

In one embodiment, by way of example only, the term “similarity elements” may be calculated based on the data and facilitate a global search for data which is similar to input data in a repository of data. In general, one or more similarity elements are calculated, and represent, a large (e.g. at least 16 MB) chunk of data.

Thus, the various embodiments described herein provide various solutions for digest retrieval based on a similarity search in deduplication processing in a data deduplication system using a processor device in a computing environment. In one embodiment, by way of example only, input data is partitioned into fixed sized data chunks. Similarity elements, digest block boundaries and digest values are calculated for each of the fixed sized data chunks. Matching similarity elements are searched for in a search structure (i.e. index) containing the similarity elements for each of the fixed sized data chunks in a repository of data. Positions of similar data are located in a repository. The positions of the similar data are used to locate and load into the memory stored digest values and corresponding stored digest block boundaries of the similar data in the repository. It should be noted that in one embodiment the positions may be either physical or logical (i.e. virtual). The positions are of data inside a repository of data. The important property of a ‘position’ is that given a position (physical or logical) in the repository's data, the data in that position can be efficiently located and accessed. The digest values and the corresponding digest block boundaries are matched with the stored digest values and the corresponding stored digest block boundaries to find data matches.

Thus, the various embodiments described herein provide various solutions for digest retrieval based on a similarity search in deduplication processing in a data deduplication system using a processor device in a computing environment. In one embodiment, by way of example only, input data is partitioned into fixed sized data chunks. Similarity elements, digest block boundaries and digest values are calculated for each of the fixed sized data chunks. Matching similarity elements are searched for in a search structure (i.e. index) containing the similarity elements for each of the fixed sized data chunks in a repository of data. Positions of similar data are located in a repository. The positions of the similar data are used to locate and load into the memory stored digest values and corresponding stored digest block boundaries of the similar data in the repository. The digest values and the corresponding digest block boundaries are matched with the stored digest values and the corresponding stored digest block boundaries to find data matches

In one embodiment, the present invention provides a solution for utilizing a similarity search to load into memory the relevant digests from the repository, for efficient deduplication processing. In a data deduplication system, deduplication is performed by partitioning the data into large fixed sized chunks, and for each chunk calculating (2 things—similarity elements and digest blocks/digest values) hash values (digest block/digest value) for similarity search and digest values. The data deduplication system searches for matching similarity values of the chunks in a search structure of similarity values, and finds the positions of similar data in the repository. The data deduplication system uses these positions of similar data to locate and load into memory stored digests of the similar repository data, and matching input and repository digest values to find data matches.

In one embodiment, the present invention provides for efficient calculation of both similarity search values and segmentation (i.e. boundaries) of digest blocks using a single linear calculation of rolling hash values. In a data deduplication system, the input data is partitioned into chunks, and for each chunk a set of rolling hash values is calculated. A single linear scan of the rolling hash values produces both similarity search values and boundaries of the digest blocks of the chunk. Each rolling hash value corresponds to a consecutive window of bytes in byte offsets. The similarity search values are used to search for similar data in the repository. The digest blocks segmentation is used to calculate digest block boundaries and corresponding digest values of the chunk, for digests matching. Each rolling hash value contributes to the calculation of the similarity values and to the calculation of the digest blocks segmentations. Each rolling hash value may be discarded after contributing to the calculations. The described embodiment provides significant processing efficiency and reduction of CPU consumption, as well as considerable performance improvement.

Thus, as described above, the deduplication approach of the present invention uses a two-step process for searching data patterns during deduplication. In the first step, a large chunk of incoming data (e.g. 16 megabytes “MB”) is searched in the repository for similar (rather than identical) chunks of existing data, and the incoming chunk is partitioned accordingly into intervals, and paired with corresponding (similar) repository intervals. The similarity search structure (or “index”) used in the first step is compact and simple to maintain search within, because the elements used for a similarity search are very compact relative to the data they represent (e.g. 16 bytes representing 4 megabytes). Further included in the first step, in addition to a calculation of similarity elements, is a calculation of digest segments and respective digest values for the input chunk of data. All these calculations are based on a single calculation of rolling hash values. In the second step, reference digests of the similar repository intervals are retrieved, and then the input digests are matched with the reference digests, to identify data matches.

In one embodiment, in the similarity based deduplication approach as described herein, a stream of input data is partitioned into chunks (e.g. at least 16 MB), and each chunk is processed in two main steps. In the first step a similarity search process is applied, and positions of the most similar reference data in the repository are found. Within this step both similarity search elements and digest segments boundaries are calculated for the input chunk, based on a single linear calculation of rolling hash values. Digest values are calculated for the input chunk based on the produced segmentation, and stored in memory in the sequence of their occurrence in the input data. The positions of similar data are then used to lookup the digests of the similar reference data and load these digests into memory, also in a sequential form. Then, the input digests are matched with the reference digests to form data matches.

When deduplication of an input chunk of data is complete, the input chunk of data's associated digests are stored in the repository, to serve as reference digests for subsequent input data. The digests are stored in a linear form, which is independent of the deduplicated form by which the data these digests describe is stored, and in the sequence of their occurrence in the data. This method of storage enables efficient retrieval of sections of digests, independent of fragmentation characterizing deduplicated storage forms, and thus low on IO and computational resource consumption.

In addition, to solve the bottleneck problem as described above, in one embodiment, a deduplication system, as described herein, may use the two step approach for searching data patterns during deduplication. In the first step, a large chunk of incoming data (e.g. a few megabytes) is searched in the repository for similar (rather than identical) data chunks of existing data, and the incoming data chunk is partitioned accordingly into intervals and paired with corresponding (similar) repository intervals. In the second step, a byte-wise matching algorithm is applied on pairs of similar intervals, to identify identical sub-intervals, which are already stored in a repository of data. The similarity index used in this step is very compact and simple to maintain and search within, since the elements used for similarity search are very compact relative to the data they represent (e.g. 16 bytes representing 4 megabytes). Further included in the first step is a calculation of similarity characteristics as well as digest segments and respective digest values, of the input chunk of data. These calculations are based on a single calculation of rolling hash values. The matching algorithm of the second step relies on reading all the relevant similar data in the repository in order to compare it byte-wise to the input data. In the second step, reference digests of the similar repository intervals are retrieved, and then the input digests are matched with the reference digests, to identify data matches. This approach works very well on data sets where the generations of data have a low to moderate change rate (roughly up to 30% change rate) relative to previous generations. Such change rates are very typical for the most common use cases, and are specifically typical for data backup environments.

Thus, as described above, similarity search is used to find reference digests that are most likely to match the digests of the input data. The reference digests are retrieved in a sequence by which they occur in the reference data. This sequence includes, in addition to the digest values, the sizes of their respective segments. The digest look up operations, as described above, provides the steps of the similarity search leading to retrieval of digests of the most similar data and comparing the digests of the input data to the digests of the most similar reference data. The steps of the similarity search provides a framework of identifying the context of the reference data which is most similar to the input data, and then retrieving the digests of that most similar reference data. These retrieved reference digests are in the sequence of their occurrence in the reference data.

Thus, the present invention enables to use the information of the sequence of occurrence of the reference digests to produce secondary segmentations of the input data. The reference digest values and sizes of their respective segments are used by the present invention. Once a sequence of matches between the input data and the reference data has been found, the present invention considers each one of the mismatches, to reduce its size using the additional information of the positions and sizes of the reference segments, thus improving the effectiveness of deduplication.

Each mismatch may include data that was affected by localized changes within specific windows of bytes that have produced segment boundaries in previous versions of that data, thus causing a change in the segmentation of the input data. By using the segmentation that is in effect in the considered reference data, that is determined as similar to the input data by the similarity search procedure, and projecting this segmentation onto the input data within a data mismatch, a set of secondary segmentations is produced for the input data within the data mismatch. A set of segmentations is produced because there may be several intervals of reference data which are determined to be similar to a given input data interval. FIG. 8 illustrates this. The digest values of each of these secondary segmentations are calculated and compared to the digest values of the references. If any digest value within a mismatch is matched based on the secondary segmentations, then the size of the mismatch is reduced and deduplication is increased. Namely, the secondary segmentations produced by the current invention enable to overcome changes in the data that affect the rolling hash windows that previously produced segment boundaries on similar data.

In one embodiment, after applying the similarity search, identifying similar reference intervals, and calculating matches and mismatches based on the digest values of the input data and the reference data, the present invention provides a solution to finding additional matching data in each one of the mismatches produced by the previous steps.

The present invention considers each one of the mismatches. In one embodiment, by way of example only, let Hv, Hr, Hs, Tv, Tr and Ts be numeric input parameters. For each mismatch the Hv digests covered by a match immediately preceding the mismatch are processed, as specified next. Each of these Hv digests are searched in a digests search structure, producing Hr matching reference digests, each located at a different reference position. For each of these Hr matching reference digests, its following Hs reference digest segments are projected by their positions and sizes onto the input data, producing new secondary input digest segments. In one embodiment, a same process is applied to the Tv digests covered by a match immediately following the mismatch. These Tv input digests are matched with Tr matching reference digests. For each of these Tr matching reference digests, its preceding Ts reference digest segments are projected by their positions and sizes onto the input data, producing further new secondary input digest segments.

For each of the new secondary digest segments, respective digest values are calculated based on the input data, thus producing a set of new secondary digests for the mismatch being processed. Then, the new secondary digests are matched with the reference digests (which are already loaded into a search structure in memory), and each new match found is recorded as a new data identity, thus reducing the mismatch size, and improving the overall deduplication ratio.

In one embodiment, the secondary segmentations produced for each mismatch are used to find more matching data, and the segmentation eventually stored for the input data is its primary segmentation, to facilitate deduplication with the next generations of this data. The present invention provides an improvement over existing hash based deduplication approaches, by enabling to identify more unchanged data.

For example, in one embodiment, the present invention produces a set of secondary segmentations for each mismatch, based on reference segmentations. In one embodiment, a data deduplication process calculating digests on an input data chunk, producing data matches and mismatches based on matching of input digests with reference digests, and, for each mismatch, obtaining and applying segmentations from similar reference intervals. In one embodiment, producing the data matches and mismatches includes searching the input digests in a search structure of reference digests. The process for obtaining possible reference segmentations includes consideration of digests included in matches preceding and following the mismatch. The considered digests are matched with reference digests. In one embodiment, the matches serve as starting position for segmentations which are projected onto the input data. New digest values are calculated on the input data based on the found segmentations. The new digest values are searched in a search structure of reference digest values. Each new match found represents a new match of data.

In one embodiment, the present invention produces secondary segmentations and digests, but stores the primary segmentation and digests for the input data. In one embodiment, a data deduplication process includes calculating digests on an input data chunk using primary segmentation, obtaining and applying secondary segmentations for each mismatch based on reference data, and storing a primary segmentation and digests for the input data. In one embodiment, producing the data matches and mismatches includes searching the input digests in a search structure of reference digests. The process for obtaining possible reference segmentations includes consideration of digests included in matches preceding and following the mismatch. The considered digests are matched with reference digests. In one embodiment, the matches serve as starting position for segmentations which are projected onto the input data. New digest values are calculated on the input data based on the found segmentations. The new digest values are searched in a search structure of reference digest values. Each new match found represents a new match of data.

In one embodiment, rather than considering only the input data for determining an appropriate segment size, the present invention considers reference data in a repository of data, which was determined as similar to the input data, to derive alternative segmentations and project these segmentations onto the input data.

In one embodiment, the present invention finds additional repository digests that match input digests, which were already matched with repository digests, and from these additional matching repository digests, it derives alternative segmentations and projects these segmentation onto the input data. The present invention has a unique feature of positioning repository segments and respective digests within a context of adjacent repository segments and respective digests, which enables to project segmentations from repository data sections onto the input data.

In one embodiment, alternative segmentations to be applied on the input data are not pre-determined and not arbitrary, but rather are derived from the segmentations of repository data that was determined as similar to the input data. Essentially, the present invention locates additional repository digests that match input digests, which were already matched with repository digests, and from these additional matching repository digests, it derives alternative segmentations and projects these segmentation onto the input data.

In one embodiment, since the new segmentations are derived from repository data that is determined to be similar to the input data, the probability that the additional segmentations will enable to find additional data matches and improve deduplication is considerably high. For example, in one embodiment, the present invention generates additional segmentations for the input data, derived from segmentations of similar repository data, and projects these additional segmentations onto the input data to improve deduplication.

Turning now to FIG. 1, exemplary architecture 10 of a computing system environment is depicted. The computer system 10 includes central processing unit (CPU) 12, which is connected to communication port 18 and memory device 16. The communication port 18 is in communication with a communication network 20. The communication network 20 and storage network may be configured to be in communication with server (hosts) 24 and storage systems, which may include storage devices 14. The storage systems may include hard disk drive (HDD) devices, solid-state devices (SSD) etc., which may be configured in a redundant array of independent disks (RAID). The operations as described below may be executed on storage device(s) 14, located in system 10 or elsewhere and may have multiple memory devices 16 working independently and/or in conjunction with other CPU devices 12. Memory device 16 may include such memory as electrically erasable programmable read only memory (EEPROM) or a host of related devices. Memory device 16 and storage devices 14 are connected to CPU 12 via a signal-bearing medium. In addition, CPU 12 is connected through communication port 18 to a communication network 20, having an attached plurality of additional computer host systems 24. In addition, memory device 16 and the CPU 12 may be embedded and included in each component of the computing system 10. Each storage system may also include separate and/or distinct memory devices 16 and CPU 12 that work in conjunction or as a separate memory device 16 and/or CPU 12.

FIG. 2 is an exemplary block diagram 200 showing a hardware structure of a data storage system in a computer system according to the present invention. Host computers 210, 220, 225, are shown, each acting as a central processing unit for performing data processing as part of a data storage system 200. The cluster hosts/nodes (physical or virtual devices), 210, 220, and 225 may be one or more new physical devices or logical devices to accomplish the purposes of the present invention in the data storage system 200. In one embodiment, by way of example only, a data storage system 200 may be implemented as IBM® ProtecTIER® deduplication system TS7650G™. A Network connection 260 may be a fibre channel fabric, a fibre channel point to point link, a fibre channel over ethernet fabric or point to point link, a FICON or ESCON I/O interface, any other I/O interface type, a wireless network, a wired network, a LAN, a WAN, heterogeneous, homogeneous, public (i.e. the Internet), private, or any combination thereof. The hosts, 210, 220, and 225 may be local or distributed among one or more locations and may be equipped with any type of fabric (or fabric channel) (not shown in FIG. 2) or network adapter 260 to the storage controller 240, such as Fibre channel, FICON, ESCON, Ethernet, fiber optic, wireless, or coaxial adapters. Data storage system 200 is accordingly equipped with a suitable fabric (not shown in FIG. 2) or network adaptor 260 to communicate. Data storage system 200 is depicted in FIG. 2 comprising storage controllers 240 and cluster hosts 210, 220, and 225. The cluster hosts 210, 220, and 225 may include cluster nodes.

To facilitate a clearer understanding of the methods described herein, storage controller 240 is shown in FIG. 2 as a single processing unit, including a microprocessor 242, system memory 243 and nonvolatile storage (“NVS”) 216. It is noted that in some embodiments, storage controller 240 is comprised of multiple processing units, each with their own processor complex and system memory, and interconnected by a dedicated network within data storage system 200. Storage 230 (labeled as 230 a, 230 b, and 230 n in FIG. 3) may be comprised of one or more storage devices, such as storage arrays, which are connected to storage controller 240 (by a storage network) with one or more cluster hosts 210, 220, and 225 connected to each storage controller 240.

In some embodiments, the devices included in storage 230 may be connected in a loop architecture. Storage controller 240 manages storage 230 and facilitates the processing of write and read requests intended for storage 230. The system memory 243 of storage controller 240 stores program instructions and data, which the processor 242 may access for executing functions and method steps of the present invention for executing and managing storage 230 as described herein. In one embodiment, system memory 243 includes, is in association with, or is in communication with the operation software 250 for performing methods and operations described herein. As shown in FIG. 2, system memory 243 may also include or be in communication with a cache 245 for storage 230, also referred to herein as a “cache memory”, for buffering “write data” and “read data”, which respectively refer to write/read requests and their associated data. In one embodiment, cache 245 is allocated in a device external to system memory 243, yet remains accessible by microprocessor 242 and may serve to provide additional security against data loss, in addition to carrying out the operations as described in herein.

In some embodiments, cache 245 is implemented with a volatile memory and non-volatile memory and coupled to microprocessor 242 via a local bus (not shown in FIG. 2) for enhanced performance of data storage system 200. The NVS 216 included in data storage controller is accessible by microprocessor 242 and serves to provide additional support for operations and execution of the present invention as described in other figures. The NVS 216, may also referred to as a “persistent” cache, or “cache memory” and is implemented with nonvolatile memory that may or may not utilize external power to retain data stored therein. The NVS may be stored in and with the cache 245 for any purposes suited to accomplish the objectives of the present invention. In some embodiments, a backup power source (not shown in FIG. 2), such as a battery, supplies NVS 216 with sufficient power to retain the data stored therein in case of power loss to data storage system 200. In certain embodiments, the capacity of NVS 216 is less than or equal to the total capacity of cache 245.

Storage 230 may be physically comprised of one or more storage devices, such as storage arrays. A storage array is a logical grouping of individual storage devices, such as a hard disk. In certain embodiments, storage 230 is comprised of a JBOD (Just a Bunch of Disks) array or a RAID (Redundant Array of Independent Disks) array. A collection of physical storage arrays may be further combined to form a rank, which dissociates the physical storage from the logical configuration. The storage space in a rank may be allocated into logical volumes, which define the storage location specified in a write/read request.

In one embodiment, by way of example only, the storage system as shown in FIG. 2 may include a logical volume, or simply “volume,” may have different kinds of allocations. Storage 230 a, 230 b and 230 n are shown as ranks in data storage system 200, and are referred to herein as rank 230 a, 230 b and 230 n. Ranks may be local to data storage system 200, or may be located at a physically remote location. In other words, a local storage controller may connect with a remote storage controller and manage storage at the remote location. Rank 230 a is shown configured with two entire volumes, 234 and 236, as well as one partial volume 232 a. Rank 230 b is shown with another partial volume 232 b. Thus volume 232 is allocated across ranks 230 a and 230 b. Rank 230 n is shown as being fully allocated to volume 238—that is, rank 230 n refers to the entire physical storage for volume 238. From the above examples, it will be appreciated that a rank may be configured to include one or more partial and/or entire volumes. Volumes and ranks may further be divided into so-called “tracks,” which represent a fixed block of storage. A track is therefore associated with a given volume and may be given a given rank.

The storage controller 240 may include a data duplication module 255, a similarity index module 257 (e.g., a similarity search structure), and a similarity search module 259. The data duplication module 255, the similarity index module 257, and the similarity search module 259 may work in conjunction with each and every component of the storage controller 240, the hosts 210, 220, 225, and storage devices 230. The data duplication module 255, the similarity index module 257, and the similarity search module 259 may be structurally one complete module or may be associated and/or included with other individual modules. The data duplication module 255, the similarity index module 257, and the similarity search module 259 may also be located in the cache 245 or other components.

The storage controller 240 includes a control switch 241 for controlling the fiber channel protocol to the host computers 210, 220, 225, a microprocessor 242 for controlling all the storage controller 240, a nonvolatile control memory 243 for storing a microprogram (operation software) 250 for controlling the operation of storage controller 240, data for control, cache 245 for temporarily storing (buffering) data, and buffers 244 for assisting the cache 245 to read and write data, a control switch 241 for controlling a protocol to control data transfer to or from the storage devices 230, the data duplication module 255, the similarity index module 257, and the similarity search module 259, in which information may be set. Multiple buffers 244 may be implemented with the present invention to assist with the operations as described herein. In one embodiment, the cluster hosts/nodes, 210, 220, 225 and the storage controller 240 are connected through a network adaptor (this could be a fibre channel) 260 as an interface i.e., via at least one switch called “fabric.”

In one embodiment, the host computers or one or more physical or virtual devices, 210, 220, 225 and the storage controller 240 are connected through a network (this could be a fibre channel) 260 as an interface i.e., via at least one switch called “fabric.” In one embodiment, the operation of the system shown in FIG. 2 will be described. The microprocessor 242 may control the memory 243 to store command information from the host device (physical or virtual) 210 and information for identifying the host device (physical or virtual) 210. The control switch 241, the buffers 244, the cache 245, the operating software 250, the microprocessor 242, memory 243, NVS 216, data duplication module 255, the similarity index module 257, and the similarity search module 259 are in communication with each other and may be separate or one individual component(s). Also, several, if not all of the components, such as the operation software 250 may be included with the memory 243. Each of the components within the devices shown may be linked together and may be in communication with each other for purposes suited to the present invention. As mentioned above, the data duplication module 255, the similarity index module 257, and the similarity search module 259 may also be located in the cache 245 or other components. As such, the data duplication module 255, the similarity index module 257, and the similarity search module 259 maybe used as needed, based upon the storage architecture and users preferences.

As mentioned above, in one embodiment, the input data is partitioned into large fixed size chunks (e.g. 16 MB), and a similarity search procedure is applied for each input chunk. A similarity search procedure calculates compact similarity elements, based on the input chunk of data, and searches for matching similarity elements stored in a compact search structure (i.e. index) in the repository. The size of the similarity elements stored per each chunk of data is typically 32 bytes (where the chunk size is a few megabytes), thus making the search structure storing the similarity elements very compact and simple to maintain and search within.

The similarity elements are calculated by calculating rolling hash values on the chunk's data, namely producing a rolling hash value for each consecutive window of bytes in a byte offset, and then selecting specific hash values and associated positions (not necessarily the exact positions of these hash values) to be the similarity elements of the chunk.

One important aspect and novelty provided by the present invention is that a single linear calculation of rolling hash values, which is a computationally expensive operation, serves as basis for calculating both the similarity elements of a chunk (for a similarity search) and the segmentation of the chunk's data into digest blocks (for finding exact matches). Each rolling hash value is added to the calculation of the similarity elements as well as to the calculation of the digest blocks segmentation. After being added to the two calculations, a rolling hash value can be discarded, as the need to store the rolling hash values is minimized or eliminated. This algorithmic element provides significant efficiency and reduction of CPU consumption, as well as considerable performance improvement.

In one embodiment, the similarity search procedure of the present invention produces two types of output. The first type of output is a set of positions of the most similar reference data in the repository. The second type of output is the digests of the input chunk, comprising of the segmentation to digest blocks and the digest values corresponding to the digest blocks, where the digest values are calculated based on the data of the digest blocks.

In one embodiment, the digests are stored in the repository in a form that corresponds to the digests occurrence in the data. Given a position in the repository and size of a section of data, the location in the repository of the digests corresponding to that interval of data is efficiently determined. The positions produced by the similarity search procedure are then used to lookup the stored digests of the similar reference data, and to load these reference digests into memory. Then, rather than comparing data, the input digests and the loaded reference digests are matched. The matching process is performed by loading the reference digests into a compact search structure of digests in memory, and then for each input digest, querying the search structure of digests for existence of that digest value. Search in the search structure of digests is performed based on the digest values. If a match is found, then the input data associated with that digest is determined to be found in the repository and the position of the input data in the repository is determined based on the reference digest's position in the repository. In this case, the identity between the input data covered by the input digest, and the repository data covered by the matching reference digest, is recorded. If a match is not found then the input data associated with that digest is determined to be not found in the repository, and is recorded as new data. In one embodiment, the similarity search structure is a global search structure of similarity elements, and a memory search structure of digests' is a local search structure of digests in memory. The search in the memory search structure of digests is performed by the digest values.

FIG. 3 is a flowchart illustrating an exemplary method 300 for digest retrieval based on similarity search in deduplication processing in a data deduplication system in which aspects of the present invention may be realized. The method 300 begins (step 302). The method 300 partitions input data into data chunks (step 304). The input data may be partitioned into fixed sized data chunks. The method 300 calculates, for each of the data chunks, similarity elements, digest block boundaries, and corresponding digest values are calculated (step 306). The method 300 searches for matching similarity elements in a search structure (i.e. index) for each of the data chunks (which may be fixed size data chunks) (step 308). The positions of the similar data in a repository (e.g., a repository of data) are located (step 310). The method 300 uses the positions of the similar data to locate and load into memory stored digest values and corresponding stored digest block boundaries of the similar data in the repository (step 312). The method 300 matches the digest values and the corresponding digest block boundaries of the input data with the stored digest values and the corresponding stored digest block boundaries to find data matches (step 314). The method 300 ends (step 316).

FIG. 4 is a flowchart illustrating an exemplary alternative method 400 for digest retrieval based on similarity search in deduplication processing in a data deduplication system in which aspects of the present invention may be realized. The method 400 begins (step 402). The method 400 partitions the input data into chunks (e.g., partitions the input data into large fixed size chunks) (step 404), and for an input data chunk calculates rolling hash values, similarity elements, digest block boundaries, and digest values based on data of the input data chunk (step 406). The method 400 searches for similarity elements of the input data chunk in a similarity search structure (i.e. index) (step 408 and 410). The method 400 determines if there are enough or a sufficient amount of matching similarity elements (step 412). If not enough matching similarity elements are found then the method 400 determines that no similar data is found in the repository for the input data chunk, and the data of the input chunk is stored in a repository (step 414) and then the method 400 ends (step 438). If enough similarity elements are found, then for each similar data interval found in a repository, the method 400 determines the position and size of each similar data interval in the repository (step 416). The method 400 locates the digests representing the similar data interval in the repository (step 418). The method 400 loads these digests into a search data structure of digests in memory (step 420). The method 400 determines if there are any additional similar data intervals (step 422). If yes, the method 400 returns to step 416. If no, the method 400 considers each digest of the input data chunk (step 424). The method 400 determines if the digest value exists in the memory search structure of digests (step 426). If yes, the method 400 records the identity between the input data covered by the digest and the repository data having the matching digest value (step 428). If no, the method 400 records that the input data covered by the digest is not found in the repository (step 430). From both steps 428 and 430, the method 400 determines if there are additional digests of the input data chunk (step 432). If yes, the method 400 returns to step 424. If no, method 400 removes the similarity elements of the matched data in the repository from the similarity search structure (step 434 and step 410). The method 400 adds the similarity elements of the input data chunk to the similarity search structure (step 436). The method 400 ends (step 438).

FIG. 5 is a flowchart illustrating an exemplary method 500 for efficient calculation of both similarity search values and boundaries of digest blocks using a single linear calculation of rolling hash values in a data deduplication system in which aspects of the present invention may be realized. The method 500 begins (step 502). The method 500 partitions input data into data chunks (steps 504). The data chunks may be fixed sized data chunks. The method 500 considers each consecutive window of bytes in a byte offset in the input data (step 506). The method 500 determines if there is an additional consecutive window of bytes to be processed (step 508). If yes, the method 500 calculates a rolling hash value based on the data of the consecutive window of bytes (step 510). The method 500 contributes the rolling hash value to the calculation of the similarity values and to the calculation of the digest blocks segmentations (i.e., the digest block boundaries) (step 512). The method 500 discards the rolling hash value (step 514), and returns to step 506. If no, the method 500 concludes the calculation of the similarity elements and of the digest blocks segmentation, producing the final similarity elements and digest blocks segmentation of the input data (step 516). The method 500 calculates digest values based on the digest blocks segmentation, wherein each digest block is assigned with a corresponding digest value (step 518). The similarity elements are used to search for similar data in the repository (step 520). The digest blocks and corresponding digest values are used for matching with digest blocks and corresponding digest values stored in a repository for determining data in the repository which is identical to the input data (step 522). The method 500 ends (step 524).

FIG. 6 is a block diagram illustrating calculating rolling hash values in which aspects of the present invention may be realized. A segmenting process starts with a calculation of rolling hash values (shown as H in FIG. 6 as H_(i), H_(i+1) with i being an offset of a seed) of the input data 602, of data size n, producing a hash value H at each byte position b (shown as b in FIG. 6 as b_(i), b_(i+1), b_(i+m), b_(i+m−1) with m being the seed size of m bytes), as shown below in FIG. 6. As shown, H_(i) is calculated for the seed starting at offset i based on the function f(b_(i) . . . b_(i+1)) and requires 0(m) operations. As shown, H_(i+1) can be calculated for the seed starting at offset i+1 based on the function f(b_(i+1) . . . b_(i+m)), thus requiring 0(m) operations. This operation does not constitute a rolling hash calculation. Alternatively, H_(i+1) can be calculated for the seed starting at offset i+1 based on the function g(H_(i), b_(i+m), b_(i), b_(i)), thus requiring 0(3) operations, which is considerably more efficient than the first alternative. This operation is a rolling hash calculation.

As mentioned above, there is a trade-off with regards to the size of the window of bytes based on which the rolling hash values are calculated. The rolling hash values are calculated based on a sliding window of bytes. If this sliding window is small, the rolling hash values are based on fewer bytes thus constituting a less reliable random variable, and also reducing the statistical significance of segmenting calculations which are based on these values. If the sliding window is large, then each rolling hash value is more sensitive to changes in the data (a given change in the data affects more hash values), thus making the segmenting positions more sensitive to changes in the data, as depicted below in FIG. 7, thus allowing minor or otherwise localized changes in the input data to alter the segmentation in an undesirable way. In other words, whether the window size is increased or decreased, both directions have a negative effect on the quality of the block segmentation.

FIG. 7 is a block diagram illustrating the effect of a data modification within a sliding window that determined a segment boundary in a previous generation of the data in which aspects of the present invention may be realized. FIG. 7 is a block diagram illustrating the finding of additional identical data with the secondary segmentation. FIG. 7 shows an original generation of data 702A, and a new generation of the data 704A, where in the new generation of the data 704A a byte was changed in the position 714, relative to the original generation of the data 702A. FIG. 7 further shows the original generation of the data in a segmented form 702B, and the new generation of the data in a segmented form 704B. In the original generation of the data in a segmented form 702B the position of the modified byte 714 is located within a sliding window that starts at a position marked as 706. Since the byte changed, in the new generation of the data in a segmented form 704B the sliding window starting at the same position does not yield a segmenting position, and hence there is no segment boundary generated at the position marked by 710. The data in the segment 712 did not change, but as shown in the figure the last segment in the new generation of data includes two separate segments in the original generation of data. This difference causes a difference in the calculated digest values and thus reduction in deduplication. FIG. 7 shows the start positions of the sliding windows used to declare segment boundaries 706 in both generations of the data. Also, the segment boundaries are declared at the end of the sliding windows 708.

FIG. 8 is a block diagram illustrating a method for finding additional identical data using a secondary segmentation in which aspects of the present invention may be realized. In the interval of new data 804C, two segment boundaries 808 are found (the segment boundaries are determined at the end positions of sliding windows that produced a segmenting hash value). The segment of data 816 is determined as a mismatch relative to existing data when searching hashes of segments produced by the segmentation calculated based on the new data. The data in the segment 812 did not change however, but as shown in the FIG. 8, segment 812 is not identified as unchanged data relative to existing data.

For the same interval of new data, referred to as 804D, with the same segment boundaries 808, a new segment boundary 820 is derived from the boundaries of the original data in a repository of data, and the new boundary 820 is applied to the interval of data 804D. With the new boundary 820, the hash value of segment 812 can be found in the hash values of the original data, to identify that there is no change in the data of segment 812 relative to the original data. Therefore, the new mismatch, after applying the segment boundary 820, is the mismatch depicted as 818. It can be observed that mismatch 818 is smaller than mismatch 816, thus reducing the mismatch size and increasing the effectiveness of deduplication using a secondary segmentation derived from original repository data.

FIG. 9 is a flowchart illustrating an exemplary method 900 for producing and using secondary segmentations derived from references in a data deduplication system in which aspects of the present invention may be realized. The method 900 begins (step 902). The method 900 receives an input data chunk (step 904). The method 900 segments the data using a data-based segmenting technique (step 906). Digest values are generated in accordance with the segments (step 908). The method 900 searches the input digest values in a search structure of reference digest values (step 910). The method 900 creates matches and mismatches based on the input digest values that were found and not found (step 912). The method 900 determines if there additional mismatches to process (step 914). If no, the method ends (step 926). If yes, the method 900 searches the Hv and Tv digests covered by the matches immediately preceding and following the mismatch, in a digests search structure, producing Hr and Tr matching reference digests, respectively (step 916). The method 900 projects the following Hs and preceding Ts reference digest segments by their positions and sizes onto the input data, producing new secondary input digest segments (step 918). For each of the new secondary digest segments, the method 900 calculates respective digest values based on the input data (step 920). The method 900 searches for the new secondary digests in a search structure of reference digests (step 922). For each new match found, an appropriate data identity is recorded thus reducing the mismatch size (step 924). The method 900 returns to step 914.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical fiber cable, RF, etc., or any suitable combination of the foregoing. Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Aspects of the present invention have been described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that may direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the above figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, may be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. 

What is claimed is:
 1. A method for producing a plurality of segmentations of input data into blocks in a data deduplication system using a processor device in a computing environment, comprising: calculating digests for an input data chunk using a primary segmentation by using a single linear scan of rolling hash values for calculating both the primary segmentation and similarity search values for the input data chunk, the input data chunk being at least 16 Megabytes (MB) in size; obtaining and applying secondary segmentations for each one of a plurality of data mismatches based on reference data; storing the primary segmentation and corresponding primary digests for the input data chunk in a sequence corresponding to a placement order of calculated values of the calculated digests associated with the primary digests, the placement order of the calculated values of the calculated digests correlative to an order in which input digest values were calculated such that the primary digests are stored in a linear form independent of a deduplicated form by which data the primary digests describe is stored; obtaining the segmentations for each one of the data mismatches by considering input digests included in data matches preceding and following each one of the data mismatches; and avoiding storing the secondary segmentations and corresponding secondary digests for the input data chunk.
 2. The method of claim 1, further including producing data matches and the data mismatches by searching input digests in a search structure of reference digests.
 3. The method of claim 1, further including matching the considered input digests with reference digests to produce alternative digest matches.
 4. The method of claim 3, further including defining the alternative digests matches to serve as starting positions for the secondary segmentations which are projected onto the input data.
 5. The method of claim 4, further including one of: calculating new digest values for the input data based on the secondary segmentations; and searching new digest values in a search structure of reference digest values to produce new digests matches.
 6. The method of claim 5, further including generating new data matches corresponding to the produced new digests matches.
 7. A system for producing a plurality of segmentations of input data into blocks in a data deduplication system of a computing environment, the system comprising: the data deduplication system; a repository operating in the data deduplication system; a memory in the data deduplication system; a search structure in association with the memory in the data deduplication system; and at least one processor device operable in the computing storage environment for controlling the data deduplication system, wherein the at least one processor device: calculates digests for an input data chunk using a primary segmentation by using a single linear scan of rolling hash values for calculating both the primary segmentation and similarity search values for the input data chunk, the input data chunk being at least 16 Megabytes (MB) in size, obtains and applies secondary segmentations for each one of a plurality of data mismatches based on reference data, stores the primary segmentation and corresponding primary digests for the input data chunk in a sequence corresponding to a placement order of calculated values of the calculated digests associated with the primary digests, the placement order of the calculated values of the calculated digests correlative to an order in which input digest values were calculated such that the primary digests are stored in a linear form independent of a deduplicated form by which data the primary digests describe is stored, obtains the segmentations for each one of the data mismatches by considering input digests included in data matches preceding and following each one of the data mismatches, and avoids storing the secondary segmentations and corresponding secondary digests for the input data chunk.
 8. The system of claim 7, wherein the at least one processor device produces data matches and the data mismatches by searching input digests in a search structure of reference digests.
 9. The system of claim 7, wherein the at least one processor device matches the considered input digests with reference digests to produce alternative digest matches.
 10. The system of claim 9, wherein the at least one processor device defines the alternative digests matches to serve as starting positions for the secondary segmentations which are projected onto the input data.
 11. The system of claim 10, wherein the at least one processor device performs one of: calculating new digest values for the input data based on the secondary segmentations, and searching new digest values in a search structure of reference digest values to produce new digests matches.
 12. The system of claim 11, wherein the at least one processor device generates new data matches corresponding to the produced new digests matches.
 13. A computer program product for producing a plurality of segmentations of input data into blocks in a data deduplication system using a processor device in a computing environment, the computer program product comprising a non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising: a first executable portion that calculates digests for an input data chunk using a primary segmentation by using a single linear scan of rolling hash values for calculating both the primary segmentation and similarity search values for the input data chunk, the input data chunk being at least 16 Megabytes (MB) in size; a second executable portion that obtains and applies secondary segmentations for each one of a plurality of data mismatches based on reference data; a third executable portion that stores the primary segmentation and corresponding primary digests for the input data chunk in a sequence corresponding to a placement order of calculated values of the calculated digests associated with the primary digests, the placement order of the calculated values of the calculated digests correlative to an order in which input digest values were calculated such that the primary digests are stored in a linear form independent of a deduplicated form by which data the primary digests describe is stored; a fourth executable portion that obtains the segmentations for each one of the data mismatches by considering input digests included in data matches preceding and following each one of the data mismatches; and a fifth executable portion that avoids storing the secondary segmentations and corresponding secondary digests for the input data chunk.
 14. The computer program product of claim 13, further including a sixth executable portion that produces data matches and the data mismatches by searching input digests in a search structure of reference digests.
 15. The computer program product of claim 13, further including a sixth executable portion that matches the considered input digests with reference digests to produce alternative digest matches.
 16. The computer program product of claim 15, further including a seventh executable portion that defines the alternative digests matches to serve as starting positions for the secondary segmentations which are projected onto the input data.
 17. The computer program product of claim 16, further including an eighth executable portion that performs one of: calculating new digest values for the input data based on the secondary segmentations, and searching new digest values in a search structure of reference digest values to produce new digests matches.
 18. The computer program product of claim 17, further including a ninth executable portion that generates new data matches corresponding to the produced new digests matches. 